Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Schema holder security

When you use the DataServer to create a schema holder, it accesses the ORACLE database. This section describes the ORACLE permissions required when you create a schema holder or connect to one.

Permissions for creating a schema holder

When you create or update a schema holder for an ORACLE database, you must be able to connect to the database and have SELECT privileges on specific system objects. SELECT privileges on system objects are required because the OpenEdge Data Dictionary cannot access the Data Dictionary tables in the ORACLE database without them; it must access those tables to create a schema holder.

Table 5–6 describes the permissions that you need for creating a schema holder.

Table 5–6: Required ORACLE permissions 

Permission	Object
CREATE SESSION	Database
SELECT	System objects: sys.argument$ sys.col$ sys.com$ sys.con$ sys.dual sys.icol$ sys.ind$ sys.link$ sys.obj$ sys.procedure$ sys.seq$ sys.syn$ sys.tab$ sys.ts$ sys.user$ sys.view$

Permissions for connecting a schema holder

To connect a schema holder for an ORACLE database, you must provide a valid user ID and password combination for ORACLE at connection time. Use the User ID (-U) parameter to provide the user ID and the Password (-P) parameter to provide the password.

Once you have set up the schema holder, the required ORACLE privileges vary among users depending on their applications. For example, the user running an OpenEdge application that queries, but does not update, a table in the ORACLE database must connect to the ORACLE database with a user and password that provides at least SELECT privileges on the table.

Note: In addition to the permissions required by the applications that users run, users must have SELECT permission on the sys.dual system table.

In summary, the user ID and password combination required to run an application depends on:

The ORACLE database tables the application accesses.
The type of access required on those tables.
Note: A database administrator (DBA) has to establish all user ID and password combinations within ORACLE.